Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1648

reference: 769-tree-1
name: 1648
tree-preservation-order: undefined
769-tpo-1
uprn
address-text
point: POINT (-0.962693 50.862438)
geometry: MULTIPOLYGON (((-0.962637 50.862432,-0.962639 50.862443,-0.962647 50.862453,-0.962660 50.862461,-0.962675 50.862466,-0.962693 50.862468,-0.962710 50.862467,-0.962726 50.862462,-0.962739 50.862454,-0.962747 50.862444,-0.962750 50.862433,-0.962748 50.862422,-0.962740 50.862412,-0.962728 50.862403,-0.962712 50.862398,-0.962694 50.862396,-0.962677 50.862398,-0.962661 50.862403,-0.962648 50.862411,-0.962640 50.862421,-0.962637 50.862432)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL